Temporally dynamic referential association in document collaboration systems

ABSTRACT

Various embodiments of the present invention provide methods, apparatuses, systems, computing devices, and/or the like that are configured to enable temporally dynamic referential association in document collaboration server systems. For example, certain embodiments of the present invention provide methods, apparatuses, systems, computing devices, and/or the like that are configured to perform temporally dynamic referential association in document collaboration server systems by using cross-temporal visual reference data objects, temporal visual reference data objects, cross-temporal referential association data objects, temporal referential association data objects, and administrator panel user interfaces.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. Non-Provisional ApplicationSerial No. 17/643,546 which was filed on Dec. 09, 2021, whichapplication is a continuation of U.S. Non-Provisional Application SerialNo. 17/196,511 (now U.S. Pat. No. 11,227,257) and was filed on Mar. 9,2021. Each of the aforementioned applications is hereby incorporated byreference herein in its entirety.

BACKGROUND

Various methods, apparatuses, and systems are configured to providetechniques for user interaction in document collaboration systems.Applicant has identified many deficiencies and problems associated withexisting methods, apparatuses, and systems for user interaction indocument collaboration systems. Through applied effort, ingenuity, andinnovation, these identified deficiencies and problems have been solvedby developing solutions that are in accordance with the embodiments ofthe present invention, many examples of which are described in detailherein.

BRIEF SUMMARY

In general, embodiments of the present invention provide methods,apparatuses, systems, computing devices, and/or the like that areconfigured to enable temporally dynamic referential association indocument collaboration server systems. For example, certain embodimentsof the present invention provide methods, apparatuses, systems,computing devices, and/or the like that are configured to performtemporally dynamic referential association in document collaborationserver systems by using cross-temporal visual reference data objects,temporal visual reference data objects, cross-temporal referentialassociation data objects, temporal referential association data objects,and administrator panel user interfaces.

In accordance with one aspect, a computer-implemented method isprovided. In one embodiment, the computer-implemented method comprises:receive, from a client computing device, a cross-temporal referentialassociation data object, wherein the cross-temporal referentialassociation data object is generated by the client computing devicebased on a predefined cross-temporal referential input provided by anend user profile of the client computing device, and wherein thepredefined cross-temporal referential input is associated with a firstpredefined cross-temporal referential input type designation of one ormore predefined cross-temporal referential input type designations;query a cross-temporal referential mapping data object associated withthe collaborative document data object to identify a designatedcross-temporal document administrator user profile of the group ofdocument administrator user profiles for the first predefinedcross-temporal referential input type designation, wherein thecross-temporal referential mapping data object associates eachpredefined cross-temporal referential input type designation of the oneor more predefined cross-temporal referential input type designations toa corresponding document administrator user profile of the group ofdocument administrator user profiles; and transmit a cross-temporalvisual conversion data object describing the designated cross-temporaldocument administrator user profile to the client computing device.

In accordance with another aspect, a computer program product isprovided. The computer program product may comprise at least onecomputer-readable storage medium having computer-readable program codeportions stored therein, the computer-readable program code portionscomprising executable portions configured to: receive, from a clientcomputing device, a cross-temporal referential association data object,wherein the cross-temporal referential association data object isgenerated by the client computing device based on a predefinedcross-temporal referential input provided by an end user profile of theclient computing device, and wherein the predefined cross-temporalreferential input is associated with a first predefined cross-temporalreferential input type designation of one or more predefinedcross-temporal referential input type designations; query across-temporal referential mapping data object associated with thecollaborative document data object to identify a designatedcross-temporal document administrator user profile of the group ofdocument administrator user profiles for the first predefinedcross-temporal referential input type designation, wherein thecross-temporal referential mapping data object associates eachpredefined cross-temporal referential input type designation of the oneor more predefined cross-temporal referential input type designations toa corresponding document administrator user profile of the group ofdocument administrator user profiles; and transmit a cross-temporalvisual conversion data object describing the designated cross-temporaldocument administrator user profile to the client computing device.

In accordance with yet another aspect, an apparatus comprising at leastone processor and at least one memory including computer program code isprovided. In one embodiment, the at least one memory and the computerprogram code may be configured to, with the processor, cause theapparatus to: receive, from a client computing device, a cross-temporalreferential association data object, wherein the cross-temporalreferential association data object is generated by the client computingdevice based on a predefined cross-temporal referential input providedby an end user profile of the client computing device, and wherein thepredefined cross-temporal referential input is associated with a firstpredefined cross-temporal referential input type designation of one ormore predefined cross-temporal referential input type designations;query a cross-temporal referential mapping data object associated withthe collaborative document data object to identify a designatedcross-temporal document administrator user profile of the group ofdocument administrator user profiles for the first predefinedcross-temporal referential input type designation, wherein thecross-temporal referential mapping data object associates eachpredefined cross-temporal referential input type designation of the oneor more predefined cross-temporal referential input type designations toa corresponding document administrator user profile of the group ofdocument administrator user profiles; and transmit a cross-temporalvisual conversion data object describing the designated cross-temporaldocument administrator user profile to the client computing device.

In accordance with another aspect, a computer-implemented method isprovided. In one embodiment, the computer-implemented method comprises:receiving, from a client computing device, a temporal referentialassociation data object associated with an input cyclical time perioddesignation of a plurality of cyclical time period designations, whereinthe temporal referential association data object is generated by theclient computing device based on a predefined temporal referential inputprovided by an end user profile of the client computing device, andwherein the interaction has occurred at a time period that is associatedwith the input cyclical time period designation; querying a temporalreferential mapping data object associated with the collaborativedocument data object to identify a designated temporal documentadministrator user profile of the group of document administrator userprofiles for the input cyclical time period designation, wherein thetemporal referential mapping data object associates each cyclical timeperiod designation of the plurality of cyclical time period designationsto a corresponding document administrator user profile of the group ofdocument administrator user profiles; and transmitting a temporal visualconversion data object describing the designated temporal documentadministrator user profile to the client computing device.

In accordance with another aspect, a computer program product isprovided. The computer program product may comprise at least onecomputer-readable storage medium having computer-readable program codeportions stored therein, the computer-readable program code portionscomprising executable portions configured to: receive, from a clientcomputing device, a temporal referential association data objectassociated with an input cyclical time period designation of a pluralityof cyclical time period designations, wherein the temporal referentialassociation data object is generated by the client computing devicebased on a predefined temporal referential input provided by an end userprofile of the client computing device, and wherein the interaction hasoccurred at a time period that is associated with the input cyclicaltime period designation; query a temporal referential mapping dataobject associated with the collaborative document data object toidentify a designated temporal document administrator user profile ofthe group of document administrator user profiles for the input cyclicaltime period designation, wherein the temporal referential mapping dataobject associates each cyclical time period designation of the pluralityof cyclical time period designations to a corresponding documentadministrator user profile of the group of document administrator userprofiles; and transmit a temporal visual conversion data objectdescribing the designated temporal document administrator user profileto the client computing device.

In accordance with yet another aspect, an apparatus comprising at leastone processor and at least one memory including computer program code isprovided. In one embodiment, the at least one memory and the computerprogram code may be configured to, with the processor, cause theapparatus to: receive, from a client computing device, a temporalreferential association data object associated with an input cyclicaltime period designation of a plurality of cyclical time perioddesignations, wherein the temporal referential association data objectis generated by the client computing device based on a predefinedtemporal referential input provided by an end user profile of the clientcomputing device, and wherein the interaction has occurred at a timeperiod that is associated with the input cyclical time perioddesignation; query a temporal referential mapping data object associatedwith the collaborative document data object to identify a designatedtemporal document administrator user profile of the group of documentadministrator user profiles for the input cyclical time perioddesignation, wherein the temporal referential mapping data objectassociates each cyclical time period designation of the plurality ofcyclical time period designations to a corresponding documentadministrator user profile of the group of document administrator userprofiles; and transmit a temporal visual conversion data objectdescribing the designated temporal document administrator user profileto the client computing device.

BRIEF DESCRIPTION OF THE SEVERAL VIEW OF THE DRAWINGS

Having thus described some embodiments in general terms, references willnow be made to the accompanying drawings, which are not drawn to scale,and wherein:

FIG. 1 is a block diagram of an example architecture within which atleast some embodiments of the present invention may operate.

FIG. 2 is a block diagram of an example document collaboration servercomputing device in accordance with at least some embodiments of thepresent invention.

FIG. 3 is a block diagram of an example client computing device inaccordance with at least some embodiments of the present invention.

FIG. 4 is a flowchart diagram of an example process for performingserver-side operations that are configured to enable cross-temporalreferential association in accordance with at least some embodiments ofthe present invention.

FIG. 5 is a flowchart diagram of an example process for performingclient-side operations that are configured to enable cross-temporalreferential association in accordance with at least some embodiments ofthe present invention.

FIGS. 6A-6B provide operational examples of collaborative document userinterface segments before and after entry of predefined cross-temporalreferential inputs respectively in accordance with at least someembodiments of the present invention.

FIG. 7 is a flowchart diagram of an example process for performingserver-side operations that are configured to enable temporalreferential association in accordance with at least some embodiments ofthe present invention.

FIG. 8 is a flowchart diagram of an example process for performingclient-side operations that are configured to enable temporalreferential association in accordance with at least some embodiments ofthe present invention.

FIGS. 9A-9B provide operational examples of collaborative document userinterface segments before and after entry of predefined temporalreferential inputs respectively in accordance with at least someembodiments of the present invention.

FIG. 10 provides an operational example of an administrator panel userinterface in accordance with at least some embodiments of the presentinvention.

FIG. 11 provides an operational example of a collaborative document userinterface in accordance with at least some embodiments of the presentinvention.

FIG. 12 provides an operational example of a document metadata userinterface in accordance with at least some embodiments of the presentinvention.

DETAILED DESCRIPTION OF VARIOUS EMBODIMENTS

Various embodiments of the present invention now will be described morefully hereinafter with reference to the accompanying drawings, in whichsome, but not all embodiments of the disclosure are shown. Indeed, thedisclosure may be embodied in many different forms and should not beconstrued as limited to the embodiments set forth herein. Rather, theseembodiments are provided so that this disclosure will satisfy applicablelegal requirements. The term “or” is used herein in both the alternativeand conjunctive sense, unless otherwise indicated. The terms“illustrative,” “example,” and “exemplary” are used to be examples withno indication of quality level. Like numbers refer to like elementsthroughout.

Overview

Various embodiments of the present invention address technical problemsassociated with efficiently and reliably enabling user interactions in adocument collaboration server system. The disclosed techniques can beutilized by a document collaboration server system to enable userprofiles of the noted document collaboration server systems to interactwith each other while imposing less computational load on the documentcollaboration server systems compared to existing solutions for enablinguser interactions in document collaboration server systems. An exampleof a document collaboration server system that may use theefficiency-enhancing techniques disclosed herein is the Confluence®collaborative document management platform that is owned by AtlassianPTY LTD.

Document collaboration server systems often store a large number ofcollaborative documents that are accessible/editable by a large numberuser profiles having different defined roles/responsibilities withrespect to the collaborative documents. Moreover, each collaborativedocument may at each time be accessed by a group of user profiles thatis larger than the group of user profiles that created the documents,and different portions of collaborative documents may be created bydifferent user profiles. A consequence of this complexity is that asubstantial number of processing operations need to be performed toenable user profiles to detect who to interact with in relation to aparticular collaborative document. This may in some cases requireopening new documents and/or retrieving document configuration data,both actions that when repeatedly performed impose a substantialcomputational load on a document collaboration server system.

For example, consider a collaborative document that is associated withan owner user profile, a legal support user profile, a human resourcesuser profile, and a user profile that is configured to respond questionsrelated to the collaborative document on a particular day of the week onwhich an end user profile seeks to ask such a question. Existing userinteraction solutions that facilitate user interaction in documentcollaboration server systems require that the end user profileindependently discover that, for example, @Jacob is the owner userprofile for the collaborative document, @David is the legal support userprofile for the collaborative document, @Jennifer is the human resourcesuser profile for the collaborative document, and @Sam is theday-of-the-week question responder for the collaborative document. To doso, the end user profile may retrieve relevant data definingroles/responsibilities associated with the collaborative document, anaction that imposes computational load on the document collaborationserver system.

To address the above-noted challenges associated with user-initiatedrole/responsibility queries in complex document collaboration serversystems, various embodiments of the present invention enable end-usersto generate cross-temporal references and/or temporal references thatare in turn in the backend associated with responsible documentadministrator user profiles via mapping data maintained by the documentcollaboration server systems. For example, in the example described inthe preceding paragraph, the end user profile may be able to performuser interaction by providing the following references: @owner, @legal,@HR, and @disturb, and the document collaboration server system may beconfigured to map the noted references to @Jacob, @David, @Jennifer, and@Sam respectively. In some embodiments, the document collaborationserver system even modifies the visual representation of at least someof the @owner, @legal, @HR, and @disturb references to display @Jacob,@David, @Jennifer, and @Sam respectively.

By utilizing the above-described techniques, various embodiments of thepresent invention reduce or eliminate the need for end user awareness ofparticular roles/responsibilities related to a collaborative document.This in turn reduces the need for user-initiated role/responsibilityqueries in complex document collaboration server systems, a feature thatreduces the computational load on the noted complex documentcollaboration server systems and improves the computational efficiencyand the computational reliability of the complex document collaborationserver systems.

Definitions

As used herein, the terms “data,” “content,” “digital content,” “digitalcontent object,” “information,” and similar terms may be usedinterchangeably to refer to data capable of being transmitted, received,and/or stored in accordance with embodiments of the present invention.Thus, use of any such terms should not be taken to limit the spirit andscope of embodiments of the present invention. Further, where acomputing device is described herein to receive data from anothercomputing device, it will be appreciated that the data may be receiveddirectly from another computing device or may be received indirectly viaone or more intermediary computing devices, such as, for example, one ormore servers, relays, routers, network access points, base stations,hosts, and/or the like, sometimes referred to herein as a “network.”Similarly, where a computing device is described herein to send data toanother computing device, it will be appreciated that the data may besent directly to another computing device or may be sent indirectly viaone or more intermediary computing devices, such as, for example, one ormore servers, relays, routers, network access points, base stations,hosts, and/or the like.

The terms “computer-readable storage medium” refers to a non-transitory,physical or tangible storage medium (e.g., volatile or non-volatilememory), which may be differentiated from a “computer-readabletransmission medium,” which refers to an electromagnetic signal.

The term “client computing device” refers to a combination of computerhardware and/or software that is configured to access a service madeavailable by a server. The server is often (but not always) on anothercomputer system, in which case the client accesses the service by way ofa network. Client computing devices may include, without limitation,smart phones, tablet computers, laptop computers, wearables, personalcomputers, enterprise computers, and the like.

The term “server computing device” refers to a combination of computerhardware and/or software that is configured to provide a service to aclient device. An example of a server computing device is the documentcollaboration server computing device 106 of FIG. 1 . In someembodiments, a server computing device communicates with one or moreclient computing devices using one or more computer networks.

The term “collaborative document user interface data object” refers to acollection of data items that is generated by a document collaborationserver computing device and provided by the document collaborationserver computing device to a client computing device. The collaborativedocument user interface data object describes user interface dataassociated with the collaborative document user interface and enablesthe client computing device to display the collaborative document userinterface (e.g., by executing one or more instructions defined by thecollaborative document user interface data object). In some embodiments,the collaborative document user interface data object describes markupdata associated with a collaborative document user interface, such asHypertext Markup Language (HTML) data associated with a collaborativedocument user interface.

The term “collaborative document user interface” refers to a userinterface that is generated by a client computing device based on acollaborative document user interface data object that is provided tothe client computing device by a document collaboration server computingdevice. The collaborative document user interface is configured todisplay content data associated with a corresponding collaborativedocument data object and enable an end user profile of the clientcomputing device to make one or more modifications (e.g., modifycontents of and/or add comments to) the corresponding collaborativedocument data object. For example, the collaborative document userinterface may be a web-based user interface, such as a web-based userinterface that is generated based on HTML data associated with acollaborative document user interface data object.

The term “cross-temporal referential association data object” refers toa collection of data items that is generated by a client computingdevice and provided by the client computing device to a documentcollaboration server computing device. The cross-temporal referentialassociation data object describes that an end user profile of the clientcomputing device has provided a predefined cross-temporal referentialinput while interacting with a collaborative document user interface.For example, the cross-temporal referential association data object maybe a data packet transmitted by a client computing device to a documentcollaboration server computing device that describes that an end user ofthe client computing has, while interacting with a collaborativedocument user interface, entered an @owner reference as a comment to thecollaborative document user interface. As another example, thecross-temporal referential association data object may be a data packettransmitted by a client computing device to a document collaborationserver computing device that describes that an end user of the clientcomputing has, while interacting with a collaborative document userinterface, entered an @legal reference as a comment to the collaborativedocument user interface.

The term “predefined cross-temporal referential input” refers to acollection of data items that is provided by an end user profile of aclient computing device to the client computing device. The predefinedcross-temporal referential input is provided by the end user profilewhile interacting with a collaborative document user interface that isassociated with a collaborative document data object. By providing thepredefined cross-temporal referential input while interacting withcollaborative document user interface, the end user profile isconfigured to describe that the end user profile seeks to reference adefined document administrator user profile associated with thecollaborative document data object, where the association between thedefined document administrator user profile and the collaborativedocument data object does not depend on a periodicity of a timeassociated with providing of the predefined cross-temporal referentialinput by the end user profile to the client computing device. An exampleof a predefined cross-temporal referential input is an “@owner” textinput that may describe that an end user profile seeks to references adocument administrator user profile that is deemed to be across-temporal owner of a collaborative document data object. Anotherexample of a predefined cross-temporal referential input is an “@legal”text input that may describe that an end user profile seeks toreferences a document administrator user profile that is deemed to be across-temporal legal advisor of a project related to a collaborativedocument data object.

The term “predefined cross-temporal referential input type designation”refers to a collection of data items that may be inferred by either orboth of a document collaboration server computing device or a clientcomputing device based on a predefined cross-temporal referential inputprovided by an end user profile to a client computing device whileinteracting with a collaborative document user interface associated witha collaborative document data object. The predefined cross-temporalreferential input type designation describes an inferred type of thepredefined cross-temporal referential input, where mapping thepredefined cross-temporal referential input a document administratoruser profile associated with the collaborative document data object isperformed based at least in part on the predefined cross-temporalreferential input type designation. For example, in some embodiments, an@owner predefined cross-temporal referential input may have an ownerpredefined cross-temporal referential input type designation, a featurethat causes mapping the @owner predefined cross-temporal referentialinput to an owner document administrator user profile of thecorresponding collaborative document data object. As another example, insome embodiments, an @legal predefined cross-temporal referential inputmay have a legal advisor predefined cross-temporal referential inputtype designation, a feature that causes mapping the @legal predefinedcross-temporal referential input to a legal advisor documentadministrator user profile of the corresponding collaborative documentdata object.

The term “cross-temporal referential mapping data object” refers to acollection of data items stored by a document collaboration serversystem that describes mappings between a group of predefinedcross-temporal referential input type designations and a group ofdocument administrator user profiles. Accordingly, the cross-temporalreferential mapping data object describes a designated documentadministrator user profile for each predefined cross-temporalreferential input type designation of the group of cross-temporalreferential input type designations. For example, the cross-temporalreferential mapping data object may describe that: (i) an ownerpredefined cross-temporal referential input type designation isassociated with the document administrator user profile U1, (ii) a legalpredefined cross-temporal referential input type designation isassociated with the document administrator user profile U2, (iii) ahuman resources predefined cross-temporal referential input typedesignation is associated with the document administrator user profileU3, and (iv) an accounting predefined cross-temporal referential inputtype designation is associated with the document administrator userprofile U4.

The term “cross-temporal visual reference data object” refers to acollection of data items that is generated by a document collaborationserver system and provided by the document collaboration servercomputing device to a client computing device. The cross-temporal visualreference data object describes a designated document administrator userprofile associated with a predefined cross-temporal referential inputdescribed by a cross-temporal referential association data object. Theclient computing device is configured to generate a cross-temporalreference user interface element based on the cross-temporal visualreference data object and present the cross-temporal reference userinterface element to the end user profile as part of a collaborativedocument user interface. In some embodiments, the cross-temporal visualreference data object describes markup data (e.g., HTML data) associatedwith a corresponding cross-temporal reference user interface element.

The term “cross-temporal reference user interface element” refers to auser interface element that is generated by a client computing devicebased on a cross-temporal visual reference data object and provided bythe client computing device to an end user profile of the clientcomputing device. The cross-temporal reference user interface elementmay be a user interface element that describes/depicts at least an“@[user]” text, where the user value may be a string value that isdetermined based on a textual identifier of a designated documentadministrator user profile described by the cross-temporal visualreference data object.

The term “temporal referential association data object” refers to acollection of data items that is generated by a client computing deviceand provided by the client computing device to a document collaborationserver computing device. The temporal referential association dataobject describes that an end user profile of the client computing devicehas provided a predefined temporal referential input while interactingwith a collaborative document user interface. For example, the temporalreferential association data object may be a data packet transmitted bya client computing device to a document collaboration server computingdevice that describes that an end user of the client computing has,while interacting with a collaborative document user interface, enteredan @disturb reference as a comment to the collaborative document userinterface.

The term “predefined temporal referential input” refers to a collectionof data items that is provided by an end user profile of a clientcomputing device to the client computing device. The predefined temporalreferential input is provided by the end user profile while interactingwith a collaborative document user interface that is associated with acollaborative document data object. By providing the predefined temporalreferential input while interacting with collaborative document userinterface, the end user profile is configured to describe that the enduser profile seeks to reference a defined document administrator userprofile associated with the collaborative document data object, wherethe association between the defined document administrator user profileand the collaborative document data object depends at least in part on aperiodicity of a time associated with providing of the predefinedcross-temporal referential input by the end user profile to the clientcomputing device. An example of a predefined cross-temporal referentialinput is an “@disturb” text input that may describe that an end userprofile seeks to references a document administrator user profile thatis deemed to be responsible for a collaborative document data object fora particular day of a week.

The term “cyclical time period designation” refers to a collection ofdata items that is defined based on configuration data maintained by apredictive data analysis system. The cyclical time period designationdescribes a group of time periods that are defined by a commonperiodicity of the group of time periods. For example, the cyclical timeperiod designation may describe a group of time periods that are alldeemed to fall on a particular day of the week or on particular days ofthe week. As another example, the cyclical time period designation maydescribe a group of time periods that are all deemed to fall on aparticular day of the month or on particular days of the month. As yetanother example, the cyclical time period designation may describe agroup of time periods that are all deemed to fall on a particular weekof the month or on particular weeks of the month.

The term “temporal referential mapping data object” refers to acollection of data items stored by a document collaboration serversystem that describes mappings between a group of cyclical time perioddesignations and a group of document administrator user profiles.Accordingly, the temporal referential mapping data object describes adesignated document administrator user profile for each cyclical timeperiod designation of a group of cyclical time period designations. Forexample, the temporal referential mapping data object may describe that:(i) @disturb references provided on Mondays are associated with thedocument administrator user profile U1, (ii) @disturb referencesprovided on Mondays and Tuesdays are associated with the documentadministrator user profile U2, (iii) @disturb references provided onWednesdays and Thursdays are associated with the document administratoruser profile U3, and (iv) @disturb references provided on other days ofthe week are associated with the document administrator user profile U4.

The term “temporal visual reference data object” refers to a collectionof data items that is generated by a document collaboration serversystem and provided by the document collaboration server computingdevice to a client computing device. The temporal visual reference dataobject describes a designated document administrator user profileassociated with a predefined temporal referential input described by atemporal referential association data object. The client computingdevice is configured to generate a temporal reference user interfaceelement based on the temporal visual reference data object and presentthe temporal reference user interface element to the end user profile aspart of a collaborative document user interface. In some embodiments,the temporal visual reference data object describes markup data (e.g.,HTML data) associated with a corresponding temporal reference userinterface element.

The term “temporal reference user interface element” refers to a userinterface element that is generated by a client computing device basedon a temporal visual reference data object and provided by the clientcomputing device to an end user profile of the client computing device.The temporal reference user interface element may be a user interfaceelement that describes/depicts at least an “@[user]” text, where theuser value may be a string value that is determined based on a textualidentifier of a designated document administrator user profile describedby the temporal visual reference data object.

The term “administrator panel user interface presentation request”refers to a collection of data items that is generated by a clientcomputing device and provided by the client computing device to adocument collaboration server computing device. The administrator paneluser interface presentation request describes a request by an end userof the client computing device to access an administrator panel userinterface associated with a document administrator user profile. Theadministrator panel user interface presentation request may describe anidentifier for the document administrator user profile whoseadministrator panel user interface the end user seeks to access. Theadministrator panel user interface presentation request may furtherdescribe authentication data associated with the document administratoruser profile, where the authentication data is used to determine thatthe end user profile is privileged to access the document collaborationuser interface.

The term “administrator panel user interface data object” refers to acollection of data items that is generated by a document collaborationserver computing device and provided by the document collaborationserver computing device to a client computing device. The administratorpanel user interface data object describes user interface dataassociated with an administrator panel user interface and enables theclient computing device to display the administrator panel userinterface (e.g., by executing one or more instructions defined by theadministrator panel user interface data object). In some embodiments,the administrator panel user interface data object describes markup dataassociated with an administrator panel user interface, such as HypertextMarkup Language (HTML) data associated with an administrator panel userinterface.

The term “administrator panel user interface” refers to a user interfacethat is generated by a client computing device based on an administratorpanel user interface data object that is provided to the clientcomputing device by a document collaboration server computing device.The administrator panel user interface is configured to displayadministrator data associated with a corresponding collaborativedocument data object and enable an end user profile of the clientcomputing device to make one or more modifications to the correspondingadministrator data. For example, the collaborative document userinterface may be a web-based user interface, such as a web-based userinterface that is generated based on HTML data associated with anadministrator panel user interface data object. In some embodiments, anadministrator panel user interface describes one or more cross-temporaldocument references for the corresponding document administrator userprofile using a cross-temporal reference tab of the administrator paneluser interface. In some embodiments, an administrator panel userinterface describes one or more temporal document references for thecorresponding document administrator user profile using a temporalreference tab of the administrator panel user interface.

The term “collaborative document data object” refers to a collection ofdata items that is generated by a document collaboration servercomputing device and transmitted by the document collaboration servercomputing device to the client computing device as part of acollaborative document graph-based interface object. The collaborativedocument data object describes one or more document property data fieldsassociated with a corresponding collaborative document stored in astorage subsystem of a document collaboration server system that isassociated with a document collaboration server computing device. Forexample, the collaborative document data object may describe anidentifier of the corresponding collaborative document, a revisionhistory of the corresponding collaborative document, a location of thecorresponding collaborative document, a size of the correspondingcollaborative document, and/or the like. The client computing device isconfigured to process the collaborative document data object to generatea collaborative document node element for the correspondingcollaborative document in a collaborative document graph-basedinterface, where the collaborative document node element depicts avisual representation of a collaborative document associated with thecorresponding collaborative document data object, as well as optionallythe one or more document property data fields described by thecorresponding collaborative document data object.

Example System Architecture

Methods, apparatuses, and computer program products of the presentinvention may be embodied by any of a variety of devices. For example,the method, apparatus, and computer program product of an exampleembodiment may be embodied by a networked device (e.g., an enterpriseplatform), such as a server or other network entity, configured tocommunicate with one or more devices, such as one or morequery-initiating computing devices. Additionally or alternatively, thecomputing device may include fixed computing devices, such as a personalcomputer or a computer workstation. Still further, example embodimentsmay be embodied by any of a variety of mobile devices, such as aportable digital assistant (PDA), mobile telephone, smartphone, laptopcomputer, tablet computer, wearable, or any combination of theaforementioned devices.

FIG. 1 depicts an exemplary architecture 100 for enabling referentialassociation in a document collaboration server system. The architecture100 includes a group of client computing devices 102A-C and a documentcollaboration server system 105. The document collaboration serversystem 105 is configured to store collaborative documents in a storagesubsystem 108 and provide the collaborative documents in response touser queries transmitted by the client computing devices 102A-C. Thestorage subsystem 108 is configured to store document content data aswell as document metadata. The document collaboration server computingdevice 106 is configured to receive user queries from client computingdevices 102A-C and provide document contents in response to the receiveduser queries to the client computing devices.

The client computing devices 102A-C and the document collaborationserver computing device 106 may communicate over one or more networks(e.g., network 104). A network may include any wired or wirelesscommunication network including, for example, a wired or wireless localarea network (LAN), personal area network (PAN), metropolitan areanetwork (MAN), wide area network (WAN), or the like, as well as anyhardware, software and/or firmware required to implement it (such as,e.g., network routers, etc.). For example, a network may include acellular telephone, an 802.11, 802.16, 802.20, and/or WiMax network.Further, a network may include a public network, such as the Internet, aprivate network, such as an intranet, or combinations thereof, and mayutilize a variety of networking protocols now available or laterdeveloped including, but not limited to Transmission ControlProtocol/Internet Protocol (TCP/IP) based networking protocols. Forinstance, the networking protocol may be customized to suit the needs ofthe page management system. In some embodiments, the protocol is acustom protocol of JavaScript Object Notation (JSON) objects sent via aWebsocket channel. In some embodiments, the protocol is JSON over RPC,JSON over REST/HTTP, and the like.

Exemplary Document Collaboration Server Computing Device

The document collaboration server computing device 106 may be embodiedby one or more computing systems, such as apparatus 200 shown in FIG. 2. The apparatus 200 may include processor 202, memory 204, input/outputcircuitry 206, and communications circuitry 208. The apparatus 200 maybe configured to execute the operations described herein. Although thesecomponents 202-208 are described with respect to functional limitations,it should be understood that the particular implementations necessarilyinclude the use of particular hardware. It should also be understoodthat certain of these components 202-208 may include similar or commonhardware. For example, two sets of circuitries may both leverage use ofthe same processor, network interface, storage medium, or the like toperform their associated functions, such that duplicate hardware is notrequired for each set of circuitries.

In some embodiments, the processor 202 (and/or co-processor or any otherprocessing circuitry assisting or otherwise associated with theprocessor) may be in communication with the memory 204 via a bus forpassing information among components of the apparatus. The memory 204 isnon-transitory and may include, for example, one or more volatile and/ornon-volatile memories. In other words, for example, the memory 204 maybe an electronic storage device (e.g., a computer-readable storagemedium). The memory 204 may be configured to store information, data,content, applications, instructions, or the like for enabling theapparatus to carry out various functions in accordance with exampleembodiments of the present invention.

The processor 202 may be embodied in a number of different ways and may,for example, include one or more processing devices configured toperform independently. In some preferred and non-limiting embodiments,the processor 202 may include one or more processors configured intandem via a bus to enable independent execution of instructions,pipelining, and/or multithreading. The use of the term “processingcircuitry” may be understood to include a single core processor, amulti-core processor, multiple processors internal to the apparatus,and/or remote or “cloud” processors.

In some preferred and non-limiting embodiments, the processor 202 may beconfigured to execute instructions stored in the memory 204 or otherwiseaccessible to the processor 202. In some preferred and non-limitingembodiments, the processor 202 may be configured to execute hard-codedfunctionalities. As such, whether configured by hardware or softwaremethods, or by a combination thereof, the processor 202 may represent anentity (e.g., physically embodied in circuitry) capable of performingoperations according to an embodiment of the present invention whileconfigured accordingly. Alternatively, as another example, when theprocessor 202 is embodied as an executor of software instructions, theinstructions may specifically configure the processor 202 to perform thealgorithms and/or operations described herein when the instructions areexecuted.

In some embodiments, the apparatus 200 may include input/outputcircuitry 206 that may, in turn, be in communication with processor 202to provide output to the user and, in some embodiments, to receive anindication of a user input. The input/output circuitry 206 may comprisea user interface and may include a display, and may comprise a web userinterface, a mobile application, a query-initiating computing device, akiosk, or the like. In some embodiments, the input/output circuitry 206may also include a keyboard, a mouse, a joystick, a touch screen, touchareas, soft keys, a microphone, a speaker, or other input/outputmechanisms. The processor and/or user interface circuitry comprising theprocessor may be configured to control one or more functions of one ormore user interface elements through computer program instructions(e.g., software and/or firmware) stored on a memory accessible to theprocessor (e.g., memory 204, and/or the like).

The communications circuitry 208 may be any means such as a device orcircuitry embodied in either hardware or a combination of hardware andsoftware that is configured to receive and/or transmit data from/to anetwork and/or any other device, circuitry, or module in communicationwith the apparatus 200. In this regard, the communications circuitry 208may include, for example, a network interface for enablingcommunications with a wired or wireless communication network. Forexample, the communications circuitry 208 may include one or morenetwork interface cards, antennae, buses, switches, routers, modems, andsupporting hardware and/or software, or any other device suitable forenabling communications via a network. Additionally or alternatively,the communications circuitry 208 may include the circuitry forinteracting with the antenna/antennae to cause transmission of signalsvia the antenna/antennae or to handle receipt of signals received viathe antenna/antennae.

It is also noted that all or some of the information discussed hereincan be based on data that is received, generated and/or maintained byone or more components of apparatus 200. In some embodiments, one ormore external systems (such as a remote cloud computing and/or datastorage system) may also be leveraged to provide at least some of thefunctionality discussed herein.

Exemplary Client Computing Device

Referring now to FIG. 3 , a client computing device may be embodied byone or more computing systems, such as apparatus 300 shown in FIG. 3 .The apparatus 300 may include processor 302, memory 304, input/outputcircuitry 306, and a communications circuitry 308. Although thesecomponents 302-308 are described with respect to functional limitations,it should be understood that the particular implementations necessarilyinclude the use of particular hardware. It should also be understoodthat certain of these components 302-308 may include similar or commonhardware. For example, two sets of circuitries may both leverage use ofthe same processor, network interface, storage medium, or the like toperform their associated functions, such that duplicate hardware is notrequired for each set of circuitries.

In some embodiments, the processor 302 (and/or co-processor or any otherprocessing circuitry assisting or otherwise associated with theprocessor) may be in communication with the memory 304 via a bus forpassing information among components of the apparatus. The memory 304 isnon-transitory and may include, for example, one or more volatile and/ornon-volatile memories. In other words, for example, the memory 304 maybe an electronic storage device (e.g., a computer-readable storagemedium). The memory 304 may include one or more databases. Furthermore,the memory 304 may be configured to store information, data, content,applications, instructions, or the like for enabling the apparatus 300to carry out various functions in accordance with example embodiments ofthe present invention.

The processor 302 may be embodied in a number of different ways and may,for example, include one or more processing devices configured toperform independently. In some preferred and non-limiting embodiments,the processor 302 may include one or more processors configured intandem via a bus to enable independent execution of instructions,pipelining, and/or multithreading. The use of the term “processingcircuitry” may be understood to include a single core processor, amulti-core processor, multiple processors internal to the apparatus,and/or remote or “cloud” processors.

In some preferred and non-limiting embodiments, the processor 302 may beconfigured to execute instructions stored in the memory 304 or otherwiseaccessible to the processor 302. In some preferred and non-limitingembodiments, the processor 302 may be configured to execute hard-codedfunctionalities. As such, whether configured by hardware or softwaremethods, or by a combination thereof, the processor 302 may represent anentity (e.g., physically embodied in circuitry) capable of performingoperations according to an embodiment of the present invention whileconfigured accordingly. Alternatively, as another example, when theprocessor 302 is embodied as an executor of software instructions (e.g.,computer program instructions), the instructions may specificallyconfigure the processor 302 to perform the algorithms and/or operationsdescribed herein when the instructions are executed.

In some embodiments, the apparatus 300 may include input/outputcircuitry 306 that may, in turn, be in communication with processor 302to provide output to the user and, in some embodiments, to receive anindication of a user input. The input/output circuitry 306 may comprisea user interface and may include a display, and may comprise a web userinterface, a mobile application, a query-initiating computing device, akiosk, or the like.

In embodiments in which the apparatus 300 is embodied by a limitedinteraction device, the input/output circuitry 306 includes a touchscreen and does not include, or at least does not operatively engage(i.e., when configured in a table mode), other input accessories such astactile keyboards, track pads, mice, etc. In other embodiments in whichthe apparatus is embodied by a non-limited interaction device, theinput/output circuitry 306 may include may include at least one of atactile keyboard (e.g., also referred to herein as keypad), a mouse, ajoystick, a touch screen, touch areas, soft keys, and other input/outputmechanisms. The processor and/or user interface circuitry comprising theprocessor may be configured to control one or more functions of one ormore user interface elements through computer program instructions(e.g., software and/or firmware) stored on a memory accessible to theprocessor (e.g., memory 304, and/or the like).

The communications circuitry 308 may be any means such as a device orcircuitry embodied in either hardware or a combination of hardware andsoftware that is configured to receive and/or transmit data from/to anetwork and/or any other device, circuitry, or module in communicationwith the apparatus 300. In this regard, the communications circuitry 308may include, for example, a network interface for enablingcommunications with a wired or wireless communication network. Forexample, the communications circuitry 308 may include one or morenetwork interface cards, antennae, buses, switches, routers, modems, andsupporting hardware and/or software, or any other device suitable forenabling communications via a network. Additionally or alternatively,the communications circuitry 308 may include the circuitry forinteracting with the antenna/antennae to cause transmission of signalsvia the antenna/antennae or to handle receipt of signals received viathe antenna/antennae.

It is also noted that all or some of the information discussed hereincan be based on data that is received, generated and/or maintained byone or more components of apparatus 300. In some embodiments, one ormore external systems (such as a remote cloud computing and/or datastorage system) may also be leveraged to provide at least some of thefunctionality discussed herein.

Example Data Flows and Operations

Provided below are techniques for performing temporally dynamicreferential association in document collaboration server systems.However, a person of ordinary skill in the relevant technology willrecognize that the disclosed techniques can be used to performtemporally dynamic referential association in various types ofnon-collaborative document management systems. Moreover, while variousembodiments of the present invention disclose performing cross-temporalreferential association and temporal referential association usingclient-server architectures, a person of ordinary skill in the relevanttechnology will recognize that: (i) in some embodiments, all of theoperations related to performing cross-temporal referential associationmay be performed by one computing device (e.g., a client computingdevice); and/or (ii) in some embodiments, all of the operations relatedto performing temporal referential association may be performed by onecomputing device (e.g., a client computing device).

Exemplary Server-Side Operations for Cross-Temporal ReferentialAssociation

FIG. 4 is a flowchart diagram of an example process 400 for performingserver-side operations needed to enable cross-temporal referentialassociation between a collaborative document data object and a group ofdocument administrator user profiles associated with the collaborativedocument data object. Via the various steps/operations of the process400, the document collaboration server computing device 106 can enablean end user profile of a client computing device 102A-C to generatecross-temporal references while interacting with collaborative documentuser interfaces without the need to query associations between documentadministrator user profiles and collaborative document data objects, anapproach that improves the computational load on document collaborationserver systems 105 by reducing the number of end-user-initiated queriesto the noted document collaboration server systems 105.

The process 400 begins at operation 401 when the document collaborationserver computing device 106 transmits a collaborative document userinterface data object associated with a collaborative document userinterface for the collaborative document data object to a clientcomputing device 102A-C. In some embodiments, the client computingdevice 102A-C is configured to generate the collaborative document userinterface based on the collaborative document user interface data objectand present the collaborative document user interface to an end userprofile of the client computing device 102A-C.

In general, the collaborative document user interface data object maydescribe user interface data associated with the collaborative documentuser interface and enables the client computing device to display thecollaborative document user interface (e.g., by executing one or moreinstructions defined by the collaborative document user interface dataobject). In some embodiments, the collaborative document user interfacedata object describes markup data associated with a collaborativedocument user interface, such as Hypertext Markup Language (HTML) dataassociated with a collaborative document user interface. Moreover, thecollaborative document user interface may describe a user interface thatis configured to display content data associated with a correspondingcollaborative document data object and enable an end user profile of theclient computing device to make one or more modifications (e.g., modifycontents of and/or add comments to) the corresponding collaborativedocument data object. For example, the collaborative document userinterface may be a web-based user interface, such as a web-based userinterface that is generated based on HTML data associated with acollaborative document user interface data object.

An operational example of a user interface segment 600 of acollaborative document user interface is depicted in FIGS. 6A-6B. Asdepicted in FIGS. 6A-6B, the user interface segment 600 depicts aportion of the contents of a corresponding collaborative document dataobject, along with a comment to the corresponding collaborative documentdata object.

At operation 402, the document collaboration server computing device 106receives, from the client computing device 102A-C, a cross-temporalreferential association data object. The cross-temporal referentialassociation data object may describe that an end user profile of theclient computing device 102A-C has provided a predefined cross-temporalreferential input while interacting with a collaborative document userinterface. For example, the cross-temporal referential association dataobject may be a data packet transmitted by a client computing device toa document collaboration server computing device that describes that anend user of the client computing has, while interacting with acollaborative document user interface, entered an @owner reference as acomment to the collaborative document user interface. As anotherexample, the cross-temporal referential association data object may be adata packet transmitted by a client computing device to a documentcollaboration server computing device that describes that an end user ofthe client computing has, while interacting with a collaborativedocument user interface, entered an @legal reference as a comment to thecollaborative document user interface.

In some embodiments, the cross-temporal referential association dataobject is generated by the client computing device 102A-C based on apredefined cross-temporal referential input provided by the end userprofile during an interaction of the end user profile with thecollaborative document user interface. The predefined cross-temporalreferential input may be provided by the end user profile whileinteracting with a collaborative document user interface that isassociated with a collaborative document data object. By providing thepredefined cross-temporal referential input while interacting withcollaborative document user interface, the end user profile may beconfigured to describe that the end user profile seeks to reference adefined document administrator user profile associated with thecollaborative document data object, where the association between thedefined document administrator user profile and the collaborativedocument data object does not depend on a periodicity of a timeassociated with providing of the predefined cross-temporal referentialinput by the end user profile to the client computing device. An exampleof a predefined cross-temporal referential input is an “@owner” textinput that may describe that an end user profile seeks to references adocument administrator user profile that is deemed to be across-temporal owner of a collaborative document data object. Anotherexample of a predefined cross-temporal referential input is an “@legal”text input that may describe that an end user profile seeks toreferences a document administrator user profile that is deemed to be across-temporal legal advisor of a project related to a collaborativedocument data object.

In some embodiments, the predefined cross-temporal referential input isassociated with a first predefined cross-temporal referential input typedesignation of one or more predefined cross-temporal referential inputtype designations. The predefined cross-temporal referential input typedesignation may describe an inferred type of the predefinedcross-temporal referential input, where mapping the predefinedcross-temporal referential input a document administrator user profileassociated with the collaborative document data object is performedbased at least in part on the predefined cross-temporal referentialinput type designation. For example, in some embodiments, an @ownerpredefined cross-temporal referential input may have an owner predefinedcross-temporal referential input type designation, a feature that causesmapping the @owner predefined cross-temporal referential input to anowner document administrator user profile of the correspondingcollaborative document data object. As another example, in someembodiments, an @legal predefined cross-temporal referential input mayhave a legal advisor predefined cross-temporal referential input typedesignation, a feature that causes mapping the @legal predefinedcross-temporal referential input to a legal advisor documentadministrator user profile of the corresponding collaborative documentdata object. In some embodiments, the one or more predefinedcross-temporal referential input type designations comprise one or morelabel-based predefined cross-temporal referential input typedesignations, and each label-based predefined cross-temporal referentialinput type designation of the one or more label-based predefinedcross-temporal referential input type designations is associated with areference label of one or more reference labels. In some embodiments,the one or more predefined cross-temporal referential input typedesignations comprise an owner-referenced predefined cross-temporalreferential input type designation.

An operational example of a predefined cross-temporal referential input601 is depicted in the user interface segment 600 of FIG. 6A. Asdepicted in FIG. 6A, the predefined cross-temporal referential input 601includes the text “@owner”. It should be noted that, in at least someembodiments, the text “@owner” is depicted as “@owner” before the usersubmits the text through a predefined action (e.g., through an enterkeystroke, through a space keystroke, and/or the like), as submission ofthe text causes the text to be converted to an “@[user]” text, whereuser is the designated document administrator user profile for thecross-temporal referential association data object as determined basedon a predefined cross-temporal referential input type designation of thepredefined cross-temporal referential input described by thecross-temporal referential association data object.

At operation 403, the document collaboration server computing device 106queries a cross-temporal referential mapping data object associated withthe collaborative document data object to identify a designatedcross-temporal document administrator user profile of the group ofdocument administrator user profiles for the first predefinedcross-temporal referential input type designation. In some embodiments,the cross-temporal referential mapping data object associates eachpredefined cross-temporal referential input type designation of the oneor more predefined cross-temporal referential input type designations toa corresponding document administrator user profile of the group ofdocument administrator user profiles. The cross-temporal referentialmapping data object may describe mappings between a group of predefinedcross-temporal referential input type designations and a group ofdocument administrator user profiles. Accordingly, the cross-temporalreferential mapping data object may describe a designated documentadministrator user profile for each predefined cross-temporalreferential input type designation of the group of cross-temporalreferential input type designations. For example, the cross-temporalreferential mapping data object may describe that: (i) an ownerpredefined cross-temporal referential input type designation isassociated with the document administrator user profile U1, (ii) a legalpredefined cross-temporal referential input type designation isassociated with the document administrator user profile U2, (iii) ahuman resources predefined cross-temporal referential input typedesignation is associated with the document administrator user profileU3, and (iv) an accounting predefined cross-temporal referential inputtype designation is associated with the document administrator userprofile U4.

At operation 404, the document collaboration server computing device 106generates a cross-temporal visual conversion data object based on thedesignated cross-temporal document administrator user profile. Thecross-temporal visual reference data object may describe a designateddocument administrator user profile associated with a predefinedcross-temporal referential input described by a cross-temporalreferential association data object. The client computing device 102A-Cmay be configured to generate a cross-temporal reference user interfaceelement based on the cross-temporal visual reference data object andpresent the cross-temporal reference user interface element to the enduser profile as part of a collaborative document user interface. In someembodiments, the cross-temporal visual reference data object describesmarkup data (e.g., HTML data) associated with a correspondingcross-temporal reference user interface element.

At operation 405, the document collaboration server computing device 106transmits the cross-temporal visual conversion data object to the clientcomputing device 102A-C. As described above, the client computing device102A-C may be configured to generate a cross-temporal reference userinterface element based on the cross-temporal visual reference dataobject and present the cross-temporal reference user interface elementto the end user profile as part of a collaborative document userinterface. The cross-temporal reference user interface element may be auser interface element that describes/depicts at least an “@[user]”text, where the user value may be a string value that is determinedbased on a textual identifier of a designated document administratoruser profile described by the cross-temporal visual reference dataobject. An operational example of a cross-temporal reference userinterface element is the “@Jack” text 611 depicted in the user interfacesegment 600 of FIG. 6B.

In some embodiments, the document collaboration server computing device106 is configured to receive a temporal referential mapping modificationrequest, wherein the temporal referential mapping modification requestdefines a new designated cross-temporal document administrator userprofile of the group of administrator user profiles for thecollaborative document data object; and modify the temporal referentialmapping data object based on the temporal referential mappingmodification request. In some embodiments, subsequent to modifying thetemporal referential mapping data object based on the temporalreferential mapping modification request, the document collaborationserver computing device 106 is configured to: receive, from the clientcomputing device, a second cross-temporal referential association dataobject, wherein the second cross-temporal referential association dataobject is generated by the client computing device based on thepredefined cross-temporal referential input provided by a second enduser profile during an interaction of the second end user profile withthe collaborative document user interface; query the cross-temporalreferential mapping data object associated with the collaborativedocument data object to identify the new designated cross-temporaldocument administrator user profile for the first predefinedcross-temporal referential input type designation; and transmit a secondcross-temporal visual conversion data object describing the newdesignated cross-temporal document administrator user profile to theclient computing device, wherein the client computing device isconfigured to generate a second cross-temporal reference user interfaceelement based on the second cross-temporal visual conversion data objectand present the second cross-temporal reference user interface elementto the second end user profile as part of the collaborative documentuser interface.

Exemplary Client-Side Operations for Cross-Temporal ReferentialAssociation

FIG. 5 is a flowchart diagram of an example process 500 for performingclient-side operations needed to enable cross-temporal referentialassociation between a collaborative document data object and a group ofdocument administrator user profiles associated with the collaborativedocument data object. Via the various steps/operations of the process500, a client computing device 102A-C can interact with a documentcollaboration server computing device 106 in a manner that causes thedocument collaboration server computing device 106 to enable an end userprofile of a client computing device 102A-C to generate cross-temporalreferences while interacting with collaborative document user interfaceswithout the need to query associations between document administratoruser profiles and collaborative document data objects, an approach thatimproves the computational load on document collaboration server systems105 by reducing the number of end-user-initiated queries to the noteddocument collaboration server systems 105.

The process 500 begins at operation 501 when the client computing device102A-C receives a collaborative document user interface data object fromthe document collaboration server computing device 106. In someembodiments, the client computing device 102A-C is configured togenerate the collaborative document user interface based on thecollaborative document user interface data object and present thecollaborative document user interface to an end user profile of theclient computing device 102A-C. The collaborative document userinterface data object may describe user interface data associated withthe collaborative document user interface and enables the clientcomputing device to display the collaborative document user interface(e.g., by executing one or more instructions defined by thecollaborative document user interface data object). In some embodiments,the collaborative document user interface data object describes markupdata associated with a collaborative document user interface, such asHypertext Markup Language (HTML) data associated with a collaborativedocument user interface.

At operation 502, the client computing device 102A-C generates andpresents a collaborative document user interface to an end user profileof the client computing device 102A-C based on the collaborativedocument user interface data object. The collaborative document userinterface may describe a user interface that is configured to displaycontent data associated with a corresponding collaborative document dataobject and enable an end user profile of the client computing device tomake one or more modifications (e.g., modify contents of and/or addcomments to) the corresponding collaborative document data object. Forexample, the collaborative document user interface may be a web-baseduser interface, such as a web-based user interface that is generatedbased on HTML data associated with a collaborative document userinterface data object.

At operation 503, the client computing device 102A-C receives apredefined cross-temporal referential input from an end user profile ofthe client computing device 102A-C. The predefined cross-temporalreferential input may be provided by the end user profile whileinteracting with a collaborative document user interface that isassociated with a collaborative document data object. By providing thepredefined cross-temporal referential input while interacting withcollaborative document user interface, the end user profile may beconfigured to describe that the end user profile seeks to reference adefined document administrator user profile associated with thecollaborative document data object, where the association between thedefined document administrator user profile and the collaborativedocument data object does not depend on a periodicity of a timeassociated with providing of the predefined cross-temporal referentialinput by the end user profile to the client computing device. An exampleof a predefined cross-temporal referential input is an “@owner” textinput that may describe that an end user profile seeks to references adocument administrator user profile that is deemed to be across-temporal owner of a collaborative document data object. Anotherexample of a predefined cross-temporal referential input is an “@legal”text input that may describe that an end user profile seeks toreferences a document administrator user profile that is deemed to be across-temporal legal advisor of a project related to a collaborativedocument data object.

At operation 504, the client computing device 102A-C generates (e.g.,based on the predefined cross-temporal referential input and/or based onthe predefined cross-temporal referential input type designation of thepredefined cross-temporal referential input) a cross-temporalreferential association data object and transmits the cross-temporalreferential association data object to a document collaboration servercomputing device 106. The cross-temporal referential association dataobject may describe that an end user profile of the client computingdevice 102A-C has provided a predefined cross-temporal referential inputwhile interacting with a collaborative document user interface. Forexample, the cross-temporal referential association data object may be adata packet transmitted by a client computing device to a documentcollaboration server computing device that describes that an end user ofthe client computing has, while interacting with a collaborativedocument user interface, entered an @owner reference as a comment to thecollaborative document user interface. As another example, thecross-temporal referential association data object may be a data packettransmitted by a client computing device to a document collaborationserver computing device that describes that an end user of the clientcomputing has, while interacting with a collaborative document userinterface, entered an @legal reference as a comment to the collaborativedocument user interface.

In some embodiments, the cross-temporal referential association dataobject is generated by the client computing device 102A-C based on apredefined cross-temporal referential input provided by the end userprofile during an interaction of the end user profile with thecollaborative document user interface. In some embodiments, thepredefined cross-temporal referential input is associated with a firstpredefined cross-temporal referential input type designation of one ormore predefined cross-temporal referential input type designations. Insome embodiments, the cross-temporal referential association data objectis generated by the client computing device 102A-C to describe apredefined cross-temporal referential input provided by the end userprofile during an interaction of the end user profile with thecollaborative document user interface and/or a predefined cross-temporalreferential input type designation of one or more predefinedcross-temporal referential input type designations for the notedpredefined cross-temporal referential input.

At operation 505, the client computing device 102A-C receives across-temporal visual reference data object from the documentcollaboration server computing device 106. The cross-temporal visualreference data object may describe a designated document administratoruser profile associated with a predefined cross-temporal referentialinput described by a cross-temporal referential association data object.The client computing device 102A-C may be configured to generate across-temporal reference user interface element based on thecross-temporal visual reference data object and present thecross-temporal reference user interface element to the end user profileas part of a collaborative document user interface. In some embodiments,the cross-temporal visual reference data object describes markup data(e.g., HTML data) associated with a corresponding cross-temporalreference user interface element.

At operation 506, the client computing device 102A-C generates across-temporal reference user interface element based on thecross-temporal visual reference data object. The cross-temporalreference user interface element may be a user interface element thatdescribes/depicts at least an “@[user]” text, where the user value maybe a string value that is determined based on a textual identifier of adesignated document administrator user profile described by thecross-temporal visual reference data object. An operational example of across-temporal reference user interface element is the “@Jack” text 611depicted in the user interface segment 600 of FIG. 6B.

At operation 507, the client computing device 102A-C presents thecross-temporal reference user interface element to an end user profileof the client computing device 102A-C. In some embodiments, the clientcomputing device 102A-C updates the collaborative document userinterface to display the cross-temporal reference user interface elementin a segment of the collaborative document user interface thatcorresponds to the predefined cross-temporal referential input.

Exemplary Server-Side Operations for Temporal Referential Association

FIG. 7 is a flowchart diagram of an example process 700 for performingserver-side operations needed to enable temporal referential associationbetween a collaborative document data object and a group of documentadministrator user profiles associated with the collaborative documentdata object. Via the various steps/operations of the process 700, thedocument collaboration server computing device 106 can enable an enduser profile of a client computing device 102A-C to generate temporalreferences while interacting with collaborative document user interfaceswithout the need to query associations between document administratoruser profiles and collaborative document data objects, an approach thatimproves the computational load on document collaboration server systems105 by reducing the number of end-user-initiated queries to the noteddocument collaboration server systems 105.

The process 700 begins at operation 701 when the document collaborationserver computing device 106 transmits a collaborative document userinterface data object associated with a collaborative document userinterface for the collaborative document data object to a clientcomputing device 102A-C. In some embodiments, the client computingdevice 102A-C is configured to generate the collaborative document userinterface based on the collaborative document user interface data objectand present the collaborative document user interface to an end userprofile of the client computing device 102A-C.

In general, the collaborative document user interface data object maydescribe user interface data associated with the collaborative documentuser interface and enables the client computing device to display thecollaborative document user interface (e.g., by executing one or moreinstructions defined by the collaborative document user interface dataobject). In some embodiments, the collaborative document user interfacedata object describes markup data associated with a collaborativedocument user interface, such as Hypertext Markup Language (HTML) dataassociated with a collaborative document user interface. Moreover, thecollaborative document user interface may describe a user interface thatis configured to display content data associated with a correspondingcollaborative document data object and enable an end user profile of theclient computing device to make one or more modifications (e.g., modifycontents of and/or add comments to) the corresponding collaborativedocument data object. For example, the collaborative document userinterface may be a web-based user interface, such as a web-based userinterface that is generated based on HTML data associated with acollaborative document user interface data object.

An operational example of a user interface segment 900 of acollaborative document user interface is depicted in FIGS. 9A-6B. Asdepicted in FIGS. 9A-6B, the user interface segment 900 depicts aportion of the contents of a corresponding collaborative document dataobject, along with a comment to the corresponding collaborative documentdata obj ect.

At operation 702, the document collaboration server computing device 106receives, from the client computing device 102A-C, a temporalreferential association data object. The temporal referentialassociation data object may describe that an end user profile of theclient computing device 102A-C has provided a predefined temporalreferential input while interacting with a collaborative document userinterface. For example, the temporal referential association data objectmay be a data packet transmitted by a client computing device to adocument collaboration server computing device that describes that anend user of the client computing has, while interacting with acollaborative document user interface, entered an @disturb reference asa comment to the collaborative document user interface.

In some embodiments, the temporal referential association data object isgenerated by the client computing device 102A-C based on a predefinedtemporal referential input provided by the end user profile during aninteraction of the end user profile with the collaborative document userinterface. The predefined temporal referential input may be provided bythe end user profile while interacting with a collaborative documentuser interface that is associated with a collaborative document dataobject. By providing the predefined temporal referential input whileinteracting with collaborative document user interface, the end userprofile may be configured to describe that the end user profile seeks toreference a defined document administrator user profile associated withthe collaborative document data object, where the association betweenthe defined document administrator user profile and the collaborativedocument data object depends on a periodicity of a time associated withproviding of the predefined cross-temporal referential input by the enduser profile to the client computing device. An example of a predefinedcross-temporal referential input is an “@disturb” text input that maydescribe that an end user profile seeks to references a documentadministrator user profile that is deemed to be responsible for acollaborative document data object for a particular day of a week.

In some embodiments, the predefined temporal referential input isassociated with a cyclical time period designation. The cyclical timeperiod designation may describe a group of time periods that are definedby a common periodicity of the group of time periods. For example, thecyclical time period designation may describe a group of time periodsthat are all deemed to fall on a particular day of the week or onparticular days of the week. As another example, the cyclical timeperiod designation may describe a group of time periods that are alldeemed to fall on a particular day of the month or on particular days ofthe month. As yet another example, the cyclical time period designationmay describe a group of time periods that are all deemed to fall on aparticular week of the month or on particular weeks of the month.

An operational example of a predefined temporal referential input 901 isdepicted in the user interface segment 900 of FIG. 9A. As depicted inFIG. 9A, the predefined temporal referential input 901 includes the text“@disturb”. It should be noted that, in at least some embodiments, thetext “@disturb” is depicted as “@disturb” before the user submits thetext through a predefined action (e.g., through an enter keystroke,through a space keystroke, and/or the like), as submission of the textcauses the text to be converted to an “@[user]” text, where user is thedesignated document administrator user profile for the temporalreferential association data object as determined based on a cyclicaltime period designation of the predefined temporal referential inputdescribed by the temporal referential association data object. However,in some embodiments, the above-noted conversion does not take place, and@disturb reference merely causes inclusion of the temporal reference ina temporal reference repository of a designated document administratoruser profile for the temporal referential association data object asdetermined based on a cyclical time period designation of the predefinedtemporal referential input described by the temporal referentialassociation data object.

At operation 703, the document collaboration server computing device 106queries a temporal referential mapping data object associated with thecollaborative document data object to identify a designated temporaldocument administrator user profile of the group of documentadministrator user profiles for the cyclical time period designation. Insome embodiments, the temporal referential mapping data object describesmappings between a group of cyclical time period designations and agroup of document administrator user profiles. Accordingly, the temporalreferential mapping data object may describe a designated documentadministrator user profile for each cyclical time period designation ofa group of cyclical time period designations. For example, the temporalreferential mapping data object may describe that: (i) @disturbreferences provided on Mondays are associated with the documentadministrator user profile U1, (ii) @disturb references provided onMondays and Tuesdays are associated with the document administrator userprofile U2, (iii) @disturb references provided on Wednesdays andThursdays are associated with the document administrator user profileU3, and (iv) @disturb references provided on other days of the week areassociated with the document administrator user profile U4.

At operation 704, the document collaboration server computing device 106generates a temporal visual conversion data object based on thedesignated cross-temporal document administrator user profile. Thetemporal visual reference data object may describe a designated documentadministrator user profile associated with a predefined cross-temporalreferential input described by a cross-temporal referential associationdata object. The client computing device 102A-C may be configured togenerate a temporal reference user interface element based on thetemporal visual reference data object and present the temporal referenceuser interface element to the end user profile as part of acollaborative document user interface. In some embodiments, the temporalvisual reference data object describes markup data (e.g., HTML data)associated with a corresponding temporal reference user interfaceelement.

At operation 705, the document collaboration server computing device 106transmits the temporal visual conversion data object to the clientcomputing device 102A-C. As described above, the client computing device102A-C may be configured to generate a temporal reference user interfaceelement based on the temporal visual reference data object and presentthe temporal reference user interface element to the end user profile aspart of a collaborative document user interface. The temporal referenceuser interface element may be a user interface element thatdescribes/depicts at least an “@[user]” text, where the user value maybe a string value that is determined based on a textual identifier of adesignated document administrator user profile described by the temporalvisual reference data object. An operational example of a temporalreference user interface element is the “@David” text 911 depicted inthe user interface segment 900 of FIG. 9B.

Exemplary Client-Side Operations for Temporal Referential Association

FIG. 8 is a flowchart diagram of an example process 800 for performingclient-side operations needed to enable temporal referential associationbetween a collaborative document data object and a group of documentadministrator user profiles associated with the collaborative documentdata object. Via the various steps/operations of the process 800, aclient computing device 102A-C can interact with a documentcollaboration server computing device 106 in a manner that causes thedocument collaboration server computing device 106 to enable an end userprofile of a client computing device 102A-C to generate temporalreferences while interacting with collaborative document user interfaceswithout the need to query associations between document administratoruser profiles and collaborative document data objects, an approach thatimproves the computational load on document collaboration server systems105 by reducing the number of end-user-initiated queries to the noteddocument collaboration server systems 105.

The process 800 begins at operation 801 when the client computing device102A-C receives a collaborative document user interface data object fromthe document collaboration server computing device 106. In someembodiments, the client computing device 102A-C is configured togenerate the collaborative document user interface based on thecollaborative document user interface data object and present thecollaborative document user interface to an end user profile of theclient computing device 102A-C. The collaborative document userinterface data object may describe user interface data associated withthe collaborative document user interface and enables the clientcomputing device to display the collaborative document user interface(e.g., by executing one or more instructions defined by thecollaborative document user interface data object). In some embodiments,the collaborative document user interface data object describes markupdata associated with a collaborative document user interface, such asHypertext Markup Language (HTML) data associated with a collaborativedocument user interface.

At operation 802, the client computing device 102A-C generates andpresents a collaborative document user interface to an end user profileof the client computing device 102A-C based on the collaborativedocument user interface data object. The collaborative document userinterface may describe a user interface that is configured to displaycontent data associated with a corresponding collaborative document dataobject and enable an end user profile of the client computing device tomake one or more modifications (e.g., modify contents of and/or addcomments to) the corresponding collaborative document data object. Forexample, the collaborative document user interface may be a web-baseduser interface, such as a web-based user interface that is generatedbased on HTML data associated with a collaborative document userinterface data object.

At operation 803, the client computing device 102A-C receives apredefined temporal referential input from an end user profile of theclient computing device 102A-C. The predefined temporal referentialinput may be provided by the end user profile while interacting with acollaborative document user interface that is associated with acollaborative document data object. By providing the predefined temporalreferential input while interacting with collaborative document userinterface, the end user profile may be configured to describe that theend user profile seeks to reference a defined document administratoruser profile associated with the collaborative document data object,where the association between the defined document administrator userprofile and the collaborative document data object depends at least inpart on a periodicity of a time associated with providing of thepredefined temporal referential input by the end user profile to theclient computing device. An example of a predefined temporal referentialinput is an “@disturb” text input.

At operation 804, the client computing device 102A-C generates (e.g.,based on the predefined temporal referential input and/or based on thecyclical time period designation of the predefined temporal referentialinput) a temporal referential association data object and transmits thetemporal referential association data object to a document collaborationserver computing device 106. The temporal referential association dataobject may describe that an end user profile of the client computingdevice 102A-C has provided a predefined temporal referential input whileinteracting with a collaborative document user interface. For example,the cross-temporal referential association data object may be a datapacket transmitted by a client computing device to a documentcollaboration server computing device that describes that an end user ofthe client computing has, while interacting with a collaborativedocument user interface, entered an @disturb reference as a comment tothe collaborative document user interface.

At operation 805, the client computing device 102A-C receives a temporalvisual reference data object from the document collaboration servercomputing device 106. The temporal visual reference data object maydescribe a designated document administrator user profile associatedwith a predefined cross-temporal referential input described by across-temporal referential association data object. The client computingdevice 102A-C may be configured to generate a temporal reference userinterface element based on the temporal visual reference data object andpresent the temporal reference user interface element to the end userprofile as part of a collaborative document user interface. In someembodiments, the temporal visual reference data object describes markupdata (e.g., HTML data) associated with a corresponding temporalreference user interface element.

At operation 806, the client computing device 102A-C generates atemporal reference user interface element based on the temporal visualreference data object. The temporal reference user interface element maybe a user interface element that describes/depicts at least an “@[user]”text, where the user value may be a string value that is determinedbased on a textual identifier of a designated document administratoruser profile described by the temporal visual reference data object. Anoperational example of a temporal reference user interface element isthe “@David” text 911 depicted in the user interface segment 900 of FIG.9B.

At operation 807, the client computing device 102A-C presents thetemporal reference user interface element to an end user profile of theclient computing device 102A-C. In some embodiments, the clientcomputing device 102A-C updates the collaborative document userinterface to display the temporal reference user interface element in asegment of the collaborative document user interface that corresponds tothe predefined temporal referential input.

FIG. 11 depicts an operational example of a collaborative document userinterface 1100 that depicts, as part of an in-line comment, the temporalreference user interface element 1101 and, as part of a document-relatedcomment, the cross-temporal reference user interface element 1102. Inthe collaborative document user interface 1100, user interaction withuser interface element 1103 enables clicking on a button that enablesviewing the document metadata user interface 1200 of FIG. 12 . Asdepicted in FIG. 12 , the document metadata user interface 1200 of FIG.12 displays (among other things): (i) a set of associations between aset of predefined cross-temporal referential inputs and a set ofcorresponding document administrator user profiles, using the userinterface segment 1201; (ii) a set of associations between a set ofcyclical time period designations and a set of corresponding documentadministrator user profiles, using the user interface segment 1202;(iii) document revision history data using the user interface segment1203; (iv) document label data using the user interface segment 1204;and (v) document hierarchy data using the user interface segment 1205.

Exemplary Techniques Related to Administrator Panel User Interfaces

In some embodiments, the document collaboration server computing device106 is configured to: receive, from an administrator computing deviceassociated with the designated cross-temporal document administratoruser profile of the group of document administrator user profiles, anadministrator panel user interface presentation request; generate anadministrator panel user interface data object, wherein theadministrator panel user interface data object is configured to enablepresenting an administrator panel user interface that describes one ormore cross-temporal document references for the designatedcross-temporal document administrator user profile using across-temporal reference tab of the administrator panel user interface;and transmit the administrator panel user interface data object to theadministrator computing device, wherein the administrator computingdevice is configured to present the administrator panel user interfacebased on the administrator panel user interface data object. In someembodiments, the administrator panel user interface describes one ormore temporal document references for the designated cross-temporaldocument administrator user profile using a temporal reference tab ofthe administrator panel user interface. In some embodiments, eachcross-temporal document reference of the one or more cross-temporaldocument references is associated with a reference label (e.g., ahashtag) of one or more reference labels, and the cross-temporalreference tab is configured to enable filtering the one or morecross-temporal document references based on the one or more referencelabels.

In some embodiments, the document collaboration server computing device106 is configured to: receive, from an administrator computing deviceassociated with the designated cross-temporal document administratoruser profile of the group of document administrator user profiles, anadministrator panel user interface presentation request; generate anadministrator panel user interface data object, wherein theadministrator panel user interface data object is configured to enablepresenting an administrator panel user interface that describes one ormore temporal document references for the designated cross-temporaldocument administrator user profile using a temporal reference tab ofthe administrator panel user interface; and transmit the administratorpanel user interface data object to the administrator computing device,wherein the administrator computing device is configured to present theadministrator panel user interface based on the administrator panel userinterface data object. In some embodiments, the administrator panel userinterface describes one or more temporal document references for thedesignated cross-temporal document administrator user profile using atemporal reference tab of the administrator panel user interface. Insome embodiments, each temporal document reference of the one or moretemporal document references is associated with a reference label (e.g.,a hashtag) of one or more reference labels, and the temporal referencetab is configured to enable filtering the one or more temporal documentreferences based on the one or more reference labels.

An administrator panel user interface may be configured to displayadministrator data associated with a corresponding collaborativedocument data object and enable an end user profile of the clientcomputing device to make one or more modifications to the correspondingadministrator data. For example, the collaborative document userinterface may be a web-based user interface, such as a web-based userinterface that is generated based on HTML data associated with anadministrator panel user interface data object. In some embodiments, anadministrator panel user interface describes one or more cross-temporaldocument references for the corresponding document administrator userprofile using a cross-temporal reference tab of the administrator paneluser interface. In some embodiments, an administrator panel userinterface describes one or more temporal document references for thecorresponding document administrator user profile using a temporalreference tab of the administrator panel user interface.

An operational example of an administrator panel user interface 1000 isdepicted in FIG. 10 . As depicted in FIG. 10 , the administrator paneluser interface 1000 includes a cross-temporal reference tab 1001 and atemporal reference tab 2. As further depicted in FIG. 10 , thecross-temporal reference tab 1001 displays a set of cross-temporalreferences for a corresponding document administrator user profile. Asfurther depicted in FIG. 10 , the administrator panel user interface1000 includes the user interface element 1003 that includes filteringreferences (e.g., cross-temporal references, temporal references, and/orthe like) based on reference labels.

Additional Implementation Details

Although example processing systems have been described in the figuresherein, implementations of the subject matter and the functionaloperations described herein can be implemented in other types of digitalelectronic circuitry, or in computer software, firmware, or hardware,including the structures disclosed in this specification and theirstructural equivalents, or in combinations of one or more of them.

Embodiments of the subject matter and the operations described hereincan be implemented in digital electronic circuitry, or in computersoftware, firmware, or hardware, including the structures disclosed inthis specification and their structural equivalents, or in combinationsof one or more of them. Embodiments of the subject matter describedherein can be implemented as one or more computer programs, i.e., one ormore modules of computer program instructions, encoded oncomputer-readable storage medium for execution by, or to control theoperation of, information/data processing apparatus. Alternatively, orin addition, the program instructions can be encoded on anartificially-generated propagated signal, e.g., a machine-generatedelectrical, optical, or electromagnetic signal, which is generated toencode information/data for transmission to suitable receiver apparatusfor execution by an information/data processing apparatus. Acomputer-readable storage medium can be, or be included in, acomputer-readable storage device, a computer-readable storage substrate,a random or serial access memory array or device, or a combination ofone or more of them. Moreover, while a computer-readable storage mediumis not a propagated signal, a computer-readable storage medium can be asource or destination of computer program instructions encoded in anartificially-generated propagated signal. The computer-readable storagemedium can also be, or be included in, one or more separate physicalcomponents or media (e.g., multiple CDs, disks, or other storagedevices).

The operations described herein can be implemented as operationsperformed by an information/data processing apparatus oninformation/data stored on one or more computer-readable storage devicesor received from other sources.

The term “data processing apparatus” encompasses all kinds of apparatus,devices, and machines for processing data, including by way of example aprogrammable processor, a computer, a system on a chip, or multipleones, or combinations, of the foregoing. The apparatus can includespecial purpose logic circuitry, e.g., an FPGA (field programmable gatearray) or an ASIC (Application Specific Integrated Circuit). Theapparatus can also include, in addition to hardware, code that createsan limited interaction mode and/or a non-limited interaction mode forthe computer program in question, e.g., code that constitutes processorfirmware, a protocol stack, a database management system, an operatingsystem, a cross-platform runtime environment, a virtual machine, or acombination of one or more of them. The apparatus and executionenvironment can realize various different computing modelinfrastructures, such as web services, distributed computing and gridcomputing infrastructures.

A computer program (also known as a program, software, softwareapplication, script, or code) can be written in any form of programminglanguage, including compiled or interpreted languages, declarative orprocedural languages, and it can be deployed in any form, including as astand-alone program or as a module, component, subroutine, object, orother unit suitable for use in a computing environment. A computerprogram may, but need not, correspond to a file in a file system. Aprogram can be stored in a portion of a file that holds other programsor information/data (e.g., one or more scripts stored in a markuplanguage page), in a single file dedicated to the program in question,or in multiple coordinated files (e.g., files that store one or moremodules, sub-programs, or portions of code). A computer program can bedeployed to be executed on one computer or on multiple computers thatare located at one site or distributed across multiple sites andinterconnected by a communication network.

The processes and logic flows described herein can be performed by oneor more programmable processors executing one or more computer programsto perform actions by operating on input information/data and generatingoutput. Processors suitable for the execution of a computer programinclude, by way of example, both general and special purposemicroprocessors, and any one or more processors of any kind of digitalcomputer. Generally, a processor will receive instructions andinformation/data from a read-only memory, a random access memory, orboth. The essential elements of a computer are a processor forperforming actions in accordance with instructions and one or morememory devices for storing instructions and data. Generally, a computerwill also include, or be operatively coupled to receive information/datafrom or transfer information/data to, or both, one or more mass storagedevices for storing data, e.g., magnetic, magneto-optical disks, oroptical disks. However, a computer need not have such devices. Devicessuitable for storing computer program instructions and information/datainclude all forms of non-volatile memory, media and memory devices,including by way of example semiconductor memory devices, e.g., EPROM,EEPROM, and flash memory devices; magnetic disks, e.g., internal harddisks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROMdisks. The processor and the memory can be supplemented by, orincorporated in, special purpose logic circuitry.

To provide for interaction with a user, embodiments of the subjectmatter described herein can be implemented on a computer having adisplay device, e.g., a CRT (cathode ray tube) or LCD (liquid crystaldisplay) monitor, for displaying information/data to the user and akeyboard and a pointing device, e.g., a mouse or a trackball, by whichthe user can provide input to the computer. Other kinds of devices canbe used to provide for interaction with a user as well; for example,feedback provided to the user can be any form of sensory feedback, e.g.,visual feedback, auditory feedback, or tactile feedback; and input fromthe user can be received in any form, including acoustic, speech, ortactile input. In addition, a computer can interact with a user bysending pages to and receiving pages from a device that is used by theuser; for example, by sending web pages to a web browser on a user’squery-initiating computing device in response to requests received fromthe web browser.

Embodiments of the subject matter described herein can be implemented ina computing system that includes a back-end component, e.g., as aninformation/data server, or that includes a middleware component, e.g.,an application server, or that includes a front-end component, e.g., aquery-initiating computing device having a graphical user interface or aweb browser through which a user can interact with an implementation ofthe subject matter described herein, or any combination of one or moresuch back-end, middleware, or front-end components. The components ofthe system can be interconnected by any form or medium of digitalinformation/data communication, e.g., a communication network. Examplesof communication networks include a local area network (“LAN”) and awide area network (“WAN”), an inter-network (e.g., the Internet), andpeer-to-peer networks (e.g., ad hoc peer-to-peer networks).

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. In someembodiments, a server transmits information/data (e.g., a HypertextMarkup Language (HTML) page) to a query-initiating computing device(e.g., for purposes of displaying information/data to and receiving userinput from a user interacting with the query-initiating computingdevice). Information/data generated at the query-initiating computingdevice (e.g., a result of the user interaction) can be received from thequery-initiating computing device at the server.

While this specification contains many specific implementation details,these should not be construed as limitations on the scope of anyinventions or of what may be claimed, but rather as description offeatures specific to particular embodiments of particular inventions.Certain features that are described herein in the context of separateembodiments can also be implemented in combination in a singleembodiment. Conversely, various features that are described in thecontext of a single embodiment can also be implemented in multipleembodiments separately or in any suitable sub-combination. Moreover,although features may be described above as acting in certaincombinations and even initially claimed as such, one or more featuresfrom a claimed combination can in some cases be excised from thecombination, and the claimed combination may be directed to asub-combination or variation of a sub-combination.

Similarly, while operations are depicted in the drawings in a particularorder, this should not be understood as requiring that such operationsbe performed in the particular order shown or in incremental order, orthat all illustrated operations be performed, to achieve desirableresults, unless described otherwise. In certain circumstances,multitasking and parallel processing may be advantageous. Moreover, theseparation of various system components in the embodiments describedabove should not be understood as requiring such separation in allembodiments, and it should be understood that the described programcomponents and systems can generally be integrated together in a singlesoftware product or packaged into multiple software products.

Thus, particular embodiments of the subject matter have been described.Other embodiments are within the scope of the following claims. In somecases, the actions recited in the claims can be performed in a differentorder and still achieve desirable results. In addition, the processesdepicted in the accompanying figures do not necessarily require theparticular order shown, or incremental order, to achieve desirableresults, unless described otherwise. In certain implementations,multitasking and parallel processing may be advantageous.

CONCLUSION

Many modifications and other embodiments of the inventions set forthherein will come to mind to one skilled in the art to which theseinventions pertain having the benefit of the teachings presented in theforegoing description and the associated drawings. Therefore, it is tobe understood that the inventions are not to be limited to the specificembodiments disclosed and that modifications and other embodiments areintended to be included within the scope of the appended claims.Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation, unlessdescribed otherwise.

1-20. (canceled)
 21. An apparatus for temporally dynamic referentialassociation between a collaborative document data object and a pluralityof document administrator user profiles associated with thecollaborative document data object, the apparatus comprising at leastone processor and at least one memory including program code, the atleast one memory and the program code configured to, with the at leastone processor, cause the apparatus to at least: receive, from a documentcollaboration server system, a collaborative document user interfacedata object; generate a collaborative document user interface based onthe collaborative document user interface data object; transmit, to thedocument collaboration server system, a temporal referential associationdata object, wherein the temporal referential association data object isgenerated based in part on a predefined temporal referential inputgenerated by an end user profile associated with the collaborativedocument user interface; receive, from the document collaboration serversystem and based on the temporal referential association data object, atemporal visual reference data object associated with a designateddocument administrator user profile; and generate, based on the temporalvisual reference data object, a temporal reference user interfaceelement.
 22. The apparatus of claim 21, wherein the designated documentadministrator user profile is associated with the collaborative documentdata object, and wherein the association between the designated documentadministrator user profile and the collaborative document data object isbased in part on a periodicity of a time associated with the generatingof the predefined temporal referential input by the end user profile.23. The apparatus of claim 22, wherein the collaborative document dataobject is associated with a collaborative document graph-based interfaceobject, and wherein the collaborative document data object describes oneor more document property data fields associated with a correspondingcollaborative document stored in a storage subsystem of the documentcollaboration server system.
 24. The apparatus of claim 23, wherein theone or more document property data fields associated with thecollaborative document data object describe at least one of anidentifier of the corresponding collaborative document, a revisionhistory of the corresponding collaborative document, a location of thecorresponding collaborative document, or a size of the correspondingcollaborative document.
 25. The apparatus of claim 24, wherein thecollaborative document data object is configured to generate acollaborative document node element for the corresponding collaborativedocument in a collaborative document graph-based interface, wherein thecollaborative document node element depicts a visual representation ofthe corresponding collaborative document associated with thecollaborative document data object, as well as the one or more documentproperty data fields associated with the collaborative document dataobject.
 26. The apparatus of claim 25, wherein the program code isfurther configured to cause the apparatus to: generate, based in part onthe collaborative document data object, a document metadata userinterface, wherein the document metadata user interface comprises atleast one of a set of associations between a set of cyclical time perioddesignations and a set of corresponding document administrator userprofiles, one or more portions of document revision history dataassociated with the corresponding collaborative document, one or moreportions of document label data, one or more portions of documenthierarchy data, or the one or more document property data fieldsassociated with the collaborative document data object.
 27. Theapparatus of claim 21, wherein the predefined temporal referential inputis characterized by at least one of a specific alphanumeric character,special character, or a combination of specific alphanumeric charactersand special characters.
 28. A computer-implemented method for temporallydynamic referential association between a collaborative document dataobject and a group of document administrator user profiles associatedwith the collaborative document data object, the computer-implementedmethod comprising: receiving, from a document collaboration serversystem, a collaborative document user interface data object; generatinga collaborative document user interface based on the collaborativedocument user interface data object; transmitting, to the documentcollaboration server system, a temporal referential association dataobject, wherein the temporal referential association data object isgenerated based in part on a predefined temporal referential inputgenerated by an end user profile associated with the collaborativedocument user interface; receiving, from the document collaborationserver system and based on the temporal referential association dataobject, a temporal visual reference data object associated with adesignated document administrator user profile; and generating, based onthe temporal visual reference data object, a temporal reference userinterface element.
 29. The computer-implemented method of claim 28,wherein the designated document administrator user profile is associatedwith the collaborative document data object, and wherein the associationbetween the designated document administrator user profile and thecollaborative document data object is based in part on a periodicity ofa time associated with the generating of the predefined temporalreferential input by the end user profile.
 30. The computer-implementedmethod of claim 29, wherein the collaborative document data object isassociated with a collaborative document graph-based interface object,and wherein the collaborative document data object describes one or moredocument property data fields associated with a correspondingcollaborative document stored in a storage subsystem of the documentcollaboration server system.
 31. The computer-implemented method ofclaim 30, wherein the one or more document property data fieldsassociated with the collaborative document data object describe at leastone of an identifier of the corresponding collaborative document, arevision history of the corresponding collaborative document, a locationof the corresponding collaborative document, or a size of thecorresponding collaborative document.
 32. The computer-implementedmethod of claim 31, wherein the collaborative document data object isconfigured to generate a collaborative document node element for thecorresponding collaborative document in a collaborative documentgraph-based interface, wherein the collaborative document node elementdepicts a visual representation of the corresponding collaborativedocument associated with the collaborative document data object, as wellas the one or more document property data fields associated with thecollaborative document data object.
 33. The computer-implemented methodof claim 32, the computer-implemented method further comprising:generating, based in part on the collaborative document data object, adocument metadata user interface, wherein the document metadata userinterface comprises at least one of a set of associations between a setof cyclical time period designations and a set of corresponding documentadministrator user profiles, one or more portions of document revisionhistory data associated with the corresponding collaborative document,one or more portions of document label data, one or more portions ofdocument hierarchy data, or the one or more document property datafields associated with the collaborative document data object.
 34. Theapparatus of claim 28, wherein the predefined temporal referential inputis characterized by at least one of a specific alphanumeric character,special character, or a combination of specific alphanumeric charactersand special characters.
 35. A computer program product for temporallydynamic referential association between a collaborative document dataobject and a plurality of document administrator user profilesassociated with the collaborative document data object, the computerprogram product comprising at least one non-transitory computer-readablestorage medium having computer-readable program code portions storedtherein, the computer-readable program code portions configured to:receive, from a document collaboration server system, a collaborativedocument user interface data object; generate a collaborative documentuser interface based on the collaborative document user interface dataobject; transmit, to the document collaboration server system, atemporal referential association data object, wherein the temporalreferential association data object is generated based in part on apredefined temporal referential input generated by an end user profileassociated with the collaborative document user interface; receive, fromthe document collaboration server system and based on the temporalreferential association data object, a temporal visual reference dataobject associated with a designated document administrator user profile;and generate, based on the temporal visual reference data object, atemporal reference user interface element.
 36. The computer programproduct of claim 35, wherein the designated document administrator userprofile is associated with the collaborative document data object, andwherein the association between the designated document administratoruser profile and the collaborative document data object is based in parton a periodicity of a time associated with the generating of thepredefined temporal referential input by the end user profile.
 37. Thecomputer program product of claim 36, wherein the collaborative documentdata object is associated with a collaborative document graph-basedinterface object, and wherein the collaborative document data objectdescribes one or more document property data fields associated with acorresponding collaborative document stored in a storage subsystem ofthe document collaboration server system.
 38. The computer programproduct of claim 37, wherein the one or more document property datafields associated with the collaborative document data object describeat least one of an identifier of the corresponding collaborativedocument, a revision history of the corresponding collaborativedocument, a location of the corresponding collaborative document, or asize of the corresponding collaborative document.
 39. The computerprogram product of claim 38, wherein the collaborative document dataobject is configured to generate a collaborative document node elementfor the corresponding collaborative document in a collaborative documentgraph-based interface, wherein the collaborative document node elementdepicts a visual representation of the corresponding collaborativedocument associated with the collaborative document data object, as wellas the one or more document property data fields associated with thecollaborative document data object.
 40. The computer program product ofclaim 39, wherein the computer-readable program code portions arefurther configured to: generate, based in part on the collaborativedocument data object, a document metadata user interface, wherein thedocument metadata user interface comprises at least one of a set ofassociations between a set of cyclical time period designations and aset of corresponding document administrator user profiles, one or moreportions of document revision history data associated with thecorresponding collaborative document, one or more portions of documentlabel data, one or more portions of document hierarchy data, or the oneor more document property data fields associated with the collaborativedocument data object.